Learning Objectives

After completing this lesson, you’ll be able to:

• Describe why debugging is an important skill.
• Distinguish between different types of log messages.
• Find the text and spatial log files.
• Explain the difference between errors and warnings.

Debugging

In this course, we’ll cover best practices for debugging your workspaces.

Even skilled FME users seldom produce new workspaces with zero defects. For that reason, all users must be aware of the debugging techniques available in FME.

Generally, debugging in FME consists of determining whether a problem has occurred and then tracking down the problem's source (for example, where it appears in the workspace). Once you have determined where a problem arises, you can investigate it.

There are various debugging techniques available in FME, and it's essential to use these in the correct order. For example, you shouldn't waste time randomly changing parameters and re-running the workspace when a simple log message explains the issue!

A logical order would be:

• Check for any problem
  • Interpret the log for warnings and errors
  • Inspect the output datasets
• Locate the problem
  • Review connection feature counts
  • Inspect the data at key stages of the translation
• Determine the problem
  • Check reader, writer, or transformer parameters at the point of failure
  • If necessary, run the workspace in feature debug mode

In software development, debugging a process after completion is called "post-mortem debugging"! We're trying to find out what caused a fatality.

Log Interpretation

FME logs contain a record of all stages and processes within a translation. The contents are vital for debugging purposes.

Log Message Types

Different message types appear in the log window, including:

• Error: An error, denoted in the log by red text and the term ERROR, indicates that a problem has caused FME to cease processing. For example, FME cannot write the output dataset because of incorrect user permissions.
• Warning: A warning, denoted by blue text and the term WARN, indicates a processing problem. The problem is sufficiently minor to allow FME to complete the translation, but you may want to check if the output was adversely affected. For example, FME cannot write features because its geometry is incompatible with the writer format. FME Workbench will drop the features from the translation and issue a warning in the log.
• Information: Information messages, denoted by the term INFORM, indicate information that may help users determine whether their translation functioned correctly. For example, FME sometimes logs confirmation of a particular dataset parameter, such as the coordinate system.
• Statistics: Statistics messages, denoted by the term STATS, provide information on various numbers relating to the translation; for example, the number of features FME read from a source dataset and the time it took to do so.

⭐ New for 2022.0: the Log window is now displayed as a table. The new Transformer column shows you which transformer an error/information message is coming from. Click the hyperlinked transformer name to navigate to the canvas element producing the message. This ability to identify where errors are occurring will make debugging workspaces more efficient.

Spatial Log File

Besides writing the log to a text file (<workspace name>.log), FME also writes a spatial log:

The spatial log is a dataset of features (in FME Feature Store format) that the log mentions. FME generates a spatial log from <Rejected> Features when Navigator > Workspace Parameters > Reader/Writer Redirect is enabled or when a Logger has Feature Logging set to "Log and Record. You can open the FFS dataset within FME Data Inspector or the Visual Preview window in FME Workbench to inspect the features and identify any problems that caused them to be rejected.

Interpreting the Log Window

The log window should be the first to check when a translation is completed. It will tell the user whether there are any concerning errors or warnings.

Errors

If an ERROR occurs, FME will likely stop the translation. There will be red text in the log and some statements such as:

Program Terminating
Translation FAILED.

There may be several ERROR messages, so scroll back up the log window and identify the first of these, which is the likely cause of the problem. For example, this message:

ERROR |Error connecting to PostgreSQL database(host='postgis.train.safe.com', port='5432', dbname='fmedata', user='fmedata', password='*'): 'FATAL: password authentication failed for user "fmedata" FATAL: password authentication failed for user "fmedata"

...is an obvious problem with authenticating a database connection.

Warnings

Even when a translation succeeds, it's essential to check the log for the following comment:

Translation was SUCCESSFUL with X warning(s)

If there are any warnings (for example, if X > 0), use the search option to look for the word WARN. Any warning messages might significantly affect the quality of the output data.

Finding the Error's Source

Click the hyperlink in the log to be taken to the object on the canvas that produced it.